This doesn't look right. Why aren't you using the manifest file? It's there explicitly so this sort of thing is not required.

There are a couple of reasons I avoided that this time.

We already have the path for firmware server builds (firmware.ardupilot.org//) for each version listed on the custom build server. We construct it in the version fetcher module.

To get the list of artifacts for a board, we just need to append the board name to it to get the exact path where that board's artifacts are stored.

We have been using this approach for quite some time. It is already used to retrieve the features.txt file. All we need to do to get the list of all versions is extend the same logic to also retrieve the list of files from there.

Using manifests.json is a much larger piece of work. We would need to download a file (over 60 MB today) asynchronously, parse it, group the entries by version and board, and then map them to the versions listed on custom.ardupilot.org (which come directly from GitHub tags).

I agree that this approach would be more correct overall, but in my opinion, extending what we already use for features.txt is the right approach for now.